Hi, We have our (Windows Server 2008 R2) file server in remote location. I have a Linux server in my location...and I am using Windows 7 Pro 64-Bit. we have Firewall to Firewall(Both are Sonicwall) VPN enabled between remote site and our location. I have a Samba Share in my Linux server. I mapped this share as "P"drive in my Windows 7 PC. While I am copying files from "File server" to local "P" drive....{ I am using xcopy command to copy the files: xcopy "\\fileserver\criss\" "P:\criss\" /Y}..it copies for few seconds and then it says " The specified network name is no longer enough". some times it copies for long time and then says the same error. I was able to do this till last week...Some how suddenly its not working...I automated this using Task Scheduler...it worked for 2 months without any issues. Everything works fine in my Windows XP PC. (Clearly it seems to be an issue with windows 7) Please help me with this.

The message seems to be reproduced incorrectly. Instead of "enough" I would expect "available". 1. Windows 7 supports SMB 2 and would set it to SMB 1 when connecting to legacy SMB 1 compatible system. sc config lanmanworkstation depend= bowser/mrxsmb10/nsi sc config mrxsmb20 start= disabled 2. What type of resolution do you use? FQDN or netbios? Do standard troubleshootinh: Issue tests with nbtstat, dlete cache,etc. 3. Have you done any configuration, installation or update. 4. Do you use any antivirus program? Try to disable it for test. 5. Is is not crossposting if you place your question into Samba community forum. Regards Milos

Milos Puchta wrote: 1. Windows 7 supports SMB 2 and would set it to SMB 1 when connecting to legacy SMB 1 compatible system. sc config lanmanworkstation depend= bowser/mrxsmb10/nsi sc config mrxsmb20 start= disabled 2. What type of resolution do you use? FQDN or netbios? Do standard troubleshootinh:  Issue tests with nbtstat, dlete cache,etc. 3. Have you done any configuration, installation or update. 4. Do you use any antivirus program? Try to disable it for test. Regards Milos Excuse me, but I think your suggestion could impair the connection to his W2008R2 file-server. First it would be nice to know, which connection breaks: the W2008R2 server connection via VPN or the local connection to the Samba server. To test this I'd suggest to try 1) to copy from the server to the local harddisk (C:) and 2) from the local harddisk (C:) to the local Samba server (P:) and see which connection errors out. Wolfgang

@ Milos. Thank you for your reply... As it was working fine for 2 months earlier...I dont think this is an issue with SMB... I use netbios for resolution... Generally In install the updateds from Microsoft...other than this, I did not installed any other application recently... I use ESET NOD32...I tried this by disabling....same issue persists As I am able to use the samba, and the same process works fine with XP without any issues...Still you want me to contact the Samba commmm?

M able to copy the files from server to local C, and able to copy to samba server.....However somehow, when I try to access the fileserver using RUN command (Eg: \\fileserver) sometimes it works fine and sometimes it wont connect and says "The Specified Network name is no longer available"....I observerd the both ways around 1-2 Hours ....

Hi, According to your last post, I assume it is a Name resolution issue. Maybe you could try to define a record that points to the file server in Host file or change NetBios name to IP address instead. Juke Chou TechNet Community Support

Kdhara wrote: M able to copy the files from server to local C, and able to copy to samba server.....However somehow, when I try to access the fileserver using RUN command (Eg:\\fileserver <file://\\fileserver>) sometimes it works fine and sometimes it wont connect and says "The Specified Network name is no longer available"....I observerd the both ways around 1-2 Hours .... So you do not have the issue, that a filecopy operation aborts in the middle of the operation as you said in your root-post, but that you sometimes cannot access your W2008R2 server via UNC-path? In this situation I'd first check, that you do not have any offline-files defined for that server (- because you need to be patient, if using this feature, as it takes awhile for this feature to detect changes in connectivity). Further as you are using Netbios name resolution and accessing a server in another subnet do you have a valid WINS-server, which has an entry for your W2008R2 server, configured on your Win7 PC - or do you have a correct entry in the LMHOSTS file for your W2008R2 server? But generally speaking it is quite normal for Netbios name resolution to fail for quite some time if the Master Browser service in your subnet changes due to a change of network topology like shutting down a computer or starting up a computer, etc. . If you don't need the browsing capabilities, which netbios delivers, it is much more reliable and quicker to use DNS as name resolution for Windows networks, too. Wolfgang